See issue #242 (I don't have write access so can't link)

OBJECTION

As I stated in survey, there are legal ramifications for the organization and for those developing guidelines or technology for guidelines. This is not a trivial matter.

"Digital" is exceedingly broad. It is important to point out that attempting to be that broad also means a potential increase legal liabilities. This adds a trickle down concern for those of us that are donating certain technologies, originally intended for web served content only.

As such I have to object — while WCAG is used for non-web development of apps anyway (because WCAG is a freely available standard) that's different than claiming in a statement that it's good for all things digital.

Do you want to create an implied liability for "digital" systems for clinical or medical use? Aerospace? Human safety?

Rethink this please. I am NOT saying it has to be limited to web, but that if you are going to extend, it also can not be at the wave of a hand, and the extensions need to be well defined.

Other standards agencies are very granular in the approach to what a given standard document covers.